Issue 48864: Use CURRENT_TIMESTAMP instead of system time#7104
Merged
labkey-nicka merged 3 commits intodevelopfrom Oct 8, 2025
Merged
Issue 48864: Use CURRENT_TIMESTAMP instead of system time#7104labkey-nicka merged 3 commits intodevelopfrom
labkey-nicka merged 3 commits intodevelopfrom
Conversation
labkey-matthewb
approved these changes
Oct 6, 2025
703fa23 to
aaeb6b0
Compare
aaeb6b0 to
5a43de1
Compare
This was referenced Oct 9, 2025
2 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Rationale
This addresses Issue 48864 and was spurred on by intermittent API test failures caused by discrepancies in server v. database time.
Related Pull Requests
Changes
NowTimestampfromStatementUtilstoSQLFragment.SQLFragment.appendValue(NowTimestamp)Table.insert()andTable.update()statement generation to useNowTimestamp.